Prerequisites for the Nodinite Log File Parser Monitoring Agent
Unlock seamless, secure, and scalable log file monitoring with the Nodinite Log File Parser Monitoring Agent. On this page, you will:
- ✅ Understand all system and network requirements for a smooth installation
- ✅ Learn how to configure user rights and firewall settings for robust security
- ✅ Discover best practices for deploying the agent on-premise or in the cloud
- ✅ Ensure compliance and minimize troubleshooting with clear, actionable guidance
This page details everything you need to successfully install and run the Nodinite Log File Parser Monitoring Agent.
Architecture: The Log File Parser Monitoring Agent connects securely to multiple SMB shares and folders, enabling end-to-end monitoring of diverse log file formats.
Please use RegEx101 or a similar tool to test your RegEx expressions. You must practice RegEx to use this agent effectively.
You can install instances of this agent on-premise using TCP/IP for local network access, or in the cloud/off-site using Service Bus Relaying.
We recommend that you keep this agent close to the installation of Nodinite Core Services. This documentation covers local network setup (usually on the Nodinite application server)
Verified | Topic |
---|---|
Software Requirements | |
What Windows User Rights does the Log File Parser Monitoring agent require? | |
What Firewall settings are required for the Log File Parser Monitoring agent? |
Software Requirements
Product | Comment |
---|---|
Windows Server | Windows 2025 Windows 2022 Windows 2019 Windows 2016 Windows 2012 R2 Windows 2012 |
.NET Framework | .NET Framework 4.8 or later New 6.0 Our recommendation is .NET Framework 4.8.1 or later |
Versions 6.0 and later require .NET Framework 4.8 or later.
Versions 5.4 and later require .NET Framework 4.6.2 or later.
Versions before 5.4 require .NET Framework 4.5.2 or later.
What Windows User Rights does the Log File Parser Monitoring agent require?
You install the agent as a Windows Service, typically on the Nodinite application server. Virtual machines are fully supported.
- Use a local named account or a domain account (preferred).
- Grant access and run-time rights
- Follow the 'How to set logon as a Windows service right' user guide for detailed instructions.
Least privileges (basic usage)
- Grant read permission to the folder where you want to check for files (and all its child folders if the 'Include child folders' option is checked)
What Firewall settings are required for the Log File Parser Monitoring agent?
The Nodinite Log File Parser Monitoring Agent requires both inbound and outbound communication:
- Between the Monitoring Service and the Nodinite Log File Parser Monitoring Agent
- Between the Nodinite Log File Parser Monitoring Agent and the Folders/SMB Shares with files to monitor
Network diagram: The agent communicates securely with the Monitoring Service and SMB shares, ensuring reliable log file access and monitoring.
1. Between the Monitoring Service and the Log File Parser Monitoring agent
You must allow the following ports on the Windows server where the agent is installed and running:
Port | Name | Inbound | Outbound | TCP | UDP | Comment |
---|---|---|---|---|---|---|
53 | DNS | The Agent needs to know where your other servers/services are (can sometimes optionally be solved using entries in the local hosts file) |
And further with 'Option 1' or 'Option 2' as documented next:
Option 1 (Local network)
Port | Name | Inbound | Outbound | TCP | UDP | Comment |
---|---|---|---|---|---|---|
8000 | RPC | Communication is initiated by the Monitoring Service |
Option 2 (Cloud/Hybrid)
Use Service Bus Relayed connections when Nodinite and the agent are on different networks.
Nodinite uses the same principle technique as the On-Premise data gateway, see 'Adjust communication settings for the on-premises data gateway' user guide.
You must open the following ports for outbound communication with '*.servicebus.windows.net' from both on-premise and off-site (Nodinite Windows Server(s) and where the agent is installed):
Port | Name | Inbound | Outbound | TCP | UDP | Comment |
---|---|---|---|---|---|---|
443 | HTTPS | Secure outbound traffic | ||||
5671, 5672 | Secure AMQP | |||||
9350 - 9354 | Net.TCP |
2. Between the Log File Parser Monitoring agent and folder locations
Additional firewall requirements may exist depending on the use of the Samba protocol, Certificates, NTLM, Kerberos, Sun RPC, and other security technologies.
SMB
Port | Name | Inbound | Outbound | TCP | UDP | Comment |
---|---|---|---|---|---|---|
53 | DNS | The Agent needs to know where your other servers/services are (can sometimes optionally be solved with user-defined entries in the hosts file in each Windows server instance), review the following 'Microsoft' user guide |
||||
135-139 | SMB | Microsoft file sharing SMB | ||||
445 | SMB | Direct-hosted SMB traffic |
Next Step
Install Log File Parser Monitoring Agent
Related Topics
Add or manage a Monitoring Agent Configuration
Monitoring
Administration